home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 21
/
Cream of the Crop 21 (Terry Blount) (October 1996).iso
/
os2
/
cfgsrt21.zip
/
CFGSORT.TXT
< prev
next >
Wrap
Text File
|
1996-09-15
|
16KB
|
414 lines
CONFIGSORT 2.1
(C)1996 by Philip A. O'Malley
1.1 INTRODUCTION
The backbone of an OS/2 system is the config.sys file. Unfortunately,
this file starts out as an organizational mess and continually gets worse as
numerous applications modify it.
Enter ConfigSort. :)
ConfigSort will process config.sys and re-organize it into something
substantially more functional. System entries are sorted into sections, and
additional entries can be optionally organized into user-defined sections or
incorporated into the default structure.
The difference is quite astounding, as I'm sure you'll agree.
1.2 A NOTE ON VERSION 2.0
Version 1.x of ConfigSort was a completely self-contained entity, with
all the application sections hardcoded into the program. With 2.0, the user
now has the option of creating their own application entries or change the
ones provided with the distribution via an external configuration file.
With this increased power comes increased potential to disrupt the
smooth running of your system. I would strongly suggest that this
documentation is read thoroughly before attempting to modify the application
configuration file or, indeed, using the program at all.
I know from the e-mail support queries that I had with 1.x that some
people (and a bigger percentage than one would think reasonable) simply
didn't bother to read the accompanying documentation either before running
the program or afterwards when things didn't work.
On your own head be it if *you* don't!
2.1 REQUIREMENTS
ConfigSort is a compiled REXX program. As a consequence you must have
REXX installed, which comes as standard in the OS/2 Warp distribution. In
addition, ConfigSort also uses the RXEXTRAS.DLL library and this must be
present within the LIBPATH: "/OS2/DLL" is usually a good place.
RXEXTRAS.DLL is included in the ConfigSort distribution.
2.2 LICENCE FOR USE
ConfigSort is an original program, copyrighted to the author. It may not
be modified in any shape or form. It can be freely distributed providing
that no charge is made beyond those to cover duplication costs and that the
original distribution archive remains unaltered.
ConfigSort is provided "as is" and any damage, actual or perceived,
caused by the program is not the liability of the author. Your use of the
program signifies your acceptance of these conditions.
If you have no problems with the above, then onwards... :)
3.1 INSTALLATION
1. Create a directory, eg. /CFGSORT, and place the main program files in
there. These are CFGSORT.EXE, CFGSORT.APP and CFGSORT.CLI.
2. Copy RXEXTRAS.DLL, found in the "/DLL" directory created when the
distribution archive was unarchived, to the LIBPATH. If in doubt copy
it to "/OS2/DLL" on the boot partition.
3. Edit CONFIG.SYS on the boot drive and add the following line:
SET CONFIGSORT=<path to the directory containing the program files>
For example,
SET CONFIGSORT=H:/CFGSORT
4. Reboot the machine.
3.2 USAGE AND SYNTAX
ConfigSort is command-line driven. All options are invoked, or prefixed,
by keywords and are:
1. /IN <FQFN>
This specifies the fully-qualified filename of the config.sys file to be
processed. This is the only required keyword.
2. /OUT <FQFN>
This specifies an output file for ConfigSort to write to.
If this keyword is not specified then the original /IN file is backed-up
with a .bak extension and then overwritten.
3. /APPCFG <FQFN>
This specifies a fully-qualified filename for the ConfigSort
applications configuration file.
4. /NOAPPS
By default, multiple entries made by an application are grouped into a
section at the end of the file. This keyword disables this facility.
5. /NOSORT
By default, all SET statements are sorted into descending alphabetical
order. This keyword disables this facility.
6. /NOUPPER
By default, all lines in the processed file are turned upper-case, with
the exception of the information associated with SET statements. This
keyword disables this facility.
3.3 EXAMPLES
This section is just intended to visualise the above into something a
little more tangible. Three examples of syntax are shown below:
1. PROCESS "F:\CONFIG.SYS" (AND BACKUP TO F:\CONFIG.BAK)
cfgsort /in f:\config.sys
2. PROCESS "F:\CONFIG.SYS" AND OUTPUT TO "F:\CONFIG.NEW"
cfgsort /in f:\config.sys /out f:\config.new
3. PROCESS "F:\CONFIG.SYS" WITH ALL OPTIONS OFF
cfgsort /in f:\config.sys /noapps /nosort /noupper
4.1 EXTERNAL CONFIGURATION FILES
Unlike v1.x, ConfigSort 2.0 and above allows you to optionally configure
how the program behaves upon execution. There are two files which may be
used for this purpose:
1. CFGSORT.CLI
This file may contain any number of command-line options which will be
executed when the program runs. Thus it is perfectly possible to set the
file up so that a standard configuration is processed and saved, using
various options, by just invoking the cfgsort.exe program itself.
As a enhancement to it's usefulness, any conflicting command-line option
specified manually when invoking the program will take presidence over
any similar option detailed in the file. Thus, an /IN statement in the
cfgsort.cli can be overriden by an /IN statement manually specified.
This file should reside in the directory which the environmental
variable CONFIGSORT points to (see 3.1). There is no way to specify an
optional location for this file as it would somewhat negate the point of
saving typing time. ;)
An example of a CFGSORT.CLI file might be:
/IN F:\CONFIG.SYS
/NOUPPER
/NOSORT
The above example would this process a config.sys file which sits in the
root directory of F:\ and rename it to config.bak (see 3.2(2)). The
optional switches /NOUPPER and /NOSORT are active.
2. CFGSORT.APP
This is the configuration file for the applications sorting. It usually
resides in the directory referenced by the CONFIGSORT environmental
variable (see 3.1), but can be optionally specified using the /APPCFG
keyword (see 3.2(3)) on the command-line. It is obviously necessary if
applications sorting is active, ie. when the /NOAPPS keyword is not
specified on the command-line.
Each application section is begun with a "SECTION" keyword, followed by
a *single* word identifying the application.
eg. SECTION EXT2
A section is not terminated by a specific keyword, but if effectively
ended when a new "SECTION" keyword is specified.
The "SECTION" keyword is followed, on a separate line, by four optional
prefix keywords, "DESC", "SET", "FILE" and "PATH":
1. DESC
This keyword allows you to specify an identifier for the
application section to be used in the processed config.sys. If this
is not specified then ConfigSort will use the identifier specified
with the "SECTION" keyword.
eg. DESC EXT2FS LINUX FILE-SYSTEM
2. SET
This keyword allows you to specify which SET statements in the
config.sys file will be grouped into the current application
section. Multiple statements may be included on the same line,
provided that they are separated by a space, or multiple SET
keywords may be used for each individual entry.
eg. SET ETC TEMP LANG
or
eg. SET ETC
SET TEMP
SET LANG
Notice that SET statements which contain spaces can be included by
substituting an exclamation-mark for